Sign 'AlphaFS.dll' with a strong name key. 'NativeError.ThrowException()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException()' ->'NativeError.ThrowException()' ->'BackupFileStream.ReadStreamInfo()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'DiskSpaceInfo.Refresh()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetDirectoryNameWithoutRootTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryName(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRoot(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRootTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.SetCurrentDirectory(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, bool, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'DirectoryInfo.DirectoryInfo(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'FileInfo.FileInfo(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string, SearchOption)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Shell32Info.Shell32Info(string, PathFormat)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string, GetFullPathOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string, GetFullPathOptions)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Shell32.PathFileExists(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumeGuid(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumePathName(string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.SetVolumeMountPoint(string, string)' 'NativeError.ThrowException(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string)' ->'NativeError.ThrowException(string)' ->'VolumeInfo.Refresh()' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string)' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string, DosDeviceAttributes)' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string)' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string)' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, DosDeviceAttributes, bool)' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, bool)' 'NativeError.ThrowException(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.SetVolumeLabel(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException()' ->'BackupFileStream.ReadStreamInfo()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.Flush()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.GetAccessControl()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.Lock(long, long)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.Read(byte[], int, int, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.Skip(long)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.Unlock(long, long)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'BackupFileStream.Write(byte[], int, int, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Directory.GetCurrentDirectory()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetFileInfoByHandle(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.Dispose()' ->'PrivilegeEnabler.Dispose()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.InternalPrivilegeEnabler(Privilege)' ->'PrivilegeEnabler.PrivilegeEnabler(Privilege, params Privilege[])' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Privilege.LookupDisplayName()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int)' ->'Privilege.LookupLuid()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Directory.SetCurrentDirectory(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'FileInfo.Length.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'FileSystemInfo.Attributes.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'FileSystemInfo.CreationTimeUtc.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'FileSystemInfo.EntryInfo.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'FileSystemInfo.LastAccessTimeUtc.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'FileSystemInfo.LastWriteTimeUtc.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileIcon(string, Shell32.FileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfo(string, FileAttributes, Shell32.FileAttributes, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32Info.Attributes.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPoint(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Volume.GetVolumePathName(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string)' ->'Volume.SetVolumeMountPoint(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(int, string, string)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'DiskSpaceInfo.Refresh()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetDirectoryNameWithoutRootTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryName(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRoot(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRootTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.SetCurrentDirectory(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, bool, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'DirectoryInfo.DirectoryInfo(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'FileInfo.FileInfo(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, DirectoryEnumerationOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string, SearchOption)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Shell32Info.Shell32Info(string, PathFormat)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string, GetFullPathOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string, GetFullPathOptions)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Shell32.PathFileExists(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumeGuid(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumePathName(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.SetVolumeMountPoint(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string)' ->'VolumeInfo.Refresh()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string, DosDeviceAttributes)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, DosDeviceAttributes, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, bool)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(string, string)' ->'Volume.SetVolumeLabel(string, string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string)' ->'FileInfo.Length.get()' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string)' ->'Volume.GetVolumeGuid(string)' 'NativeError.ThrowException(uint, string, string)' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeError.ThrowException(uint, string, string)' ->'NativeError.ThrowException(uint, string, string)' ->'OpenResourceInfo.Close()' 'OperatingSystem.IsWow64Process.get()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.IsWow64Process.get()' ->'OperatingSystem.IsWow64Process.get()' 'OperatingSystem.IsWow64Process.get()' calls into 'Marshal.ThrowExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.ThrowExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.IsWow64Process.get()' ->'OperatingSystem.IsWow64Process.get()' 'OperatingSystem.IsWow64Process.get()' calls into 'Process.GetCurrentProcess()' which has a LinkDemand. By making this call, 'Process.GetCurrentProcess()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.IsWow64Process.get()' ->'OperatingSystem.IsWow64Process.get()' 'OperatingSystem.IsWow64Process.get()' calls into 'Process.Handle.get()' which has a LinkDemand. By making this call, 'Process.Handle.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.IsWow64Process.get()' ->'OperatingSystem.IsWow64Process.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.IsServer.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.OSVersion.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.ProcessorArchitecture.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.ServicePackVersion.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.VersionName.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.IsServer.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.OSVersion.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.ProcessorArchitecture.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.ServicePackVersion.get()' 'OperatingSystem.UpdateData()' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'OperatingSystem.UpdateData()' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.VersionName.get()' Review declarative security for 'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.IsServer.get()' Review declarative security for 'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.OSVersion.get()' Review declarative security for 'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.ProcessorArchitecture.get()' Review declarative security for 'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.ServicePackVersion.get()' Review declarative security for 'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'OperatingSystem.NativeMethods.GetNativeSystemInfo(ref OperatingSystem.NativeMethods.SYSTEM_INFO)' ->'OperatingSystem.UpdateData()' ->'OperatingSystem.VersionName.get()' Review declarative security for 'OperatingSystem.NativeMethods.IsWow64Process(IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'OperatingSystem.NativeMethods.IsWow64Process(IntPtr, out bool)' ->'OperatingSystem.IsWow64Process.get()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.Read(byte[], int, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.ReadStreamInfo()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.Write(byte[], int, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedConnectionName(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedUncName(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'Marshal.AllocHGlobal(int)' which has a LinkDemand. By making this call, 'Marshal.AllocHGlobal(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.Read(byte[], int, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.ReadStreamInfo()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.Write(byte[], int, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedConnectionName(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedUncName(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'SafeGlobalMemoryBufferHandle.FromLong(long?)' calls into 'Marshal.WriteInt64(IntPtr, long)' which has a LinkDemand. By making this call, 'Marshal.WriteInt64(IntPtr, long)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle()' ->'SafeGlobalMemoryBufferHandle.FromLong(long?)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.Read(byte[], int, int, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.ReadStreamInfo()' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'BackupFileStream.Write(byte[], int, int, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedConnectionName(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedUncName(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' 'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(bool)' ->'SafeNativeMemoryBufferHandle.SafeNativeMemoryBufferHandle(int)' ->'SafeGlobalMemoryBufferHandle.SafeGlobalMemoryBufferHandle(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'BackupFileStream.Write(byte[], int, int, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' calls into 'Marshal.Copy(byte[], int, IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(byte[], int, IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyFrom(byte[], int, int)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'SafeNativeMemoryBufferHandle.CopyTo(byte[], int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyTo(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyTo(byte[], int, int)' ->'BackupFileStream.GetAccessControl()' 'SafeNativeMemoryBufferHandle.CopyTo(byte[], int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyTo(byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyTo(byte[], int, int)' ->'BackupFileStream.Read(byte[], int, int, bool)' 'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'SafeNativeMemoryBufferHandle.CopyTo(int, byte[], int, int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStringUni(int, int)' calls into 'Marshal.PtrToStringUni(IntPtr, int)' which has a LinkDemand. By making this call, 'Marshal.PtrToStringUni(IntPtr, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStringUni(int, int)' ->'SafeNativeMemoryBufferHandle.PtrToStringUni(int, int)' ->'BackupFileStream.ReadStreamInfo()' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'BackupFileStream.ReadStreamInfo()' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string, string, string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsInfo(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedConnectionName(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedUncName(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(ShareInfoLevel, string, bool)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(ShareInfoLevel, string, string, bool)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(string, bool)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(string, string, bool)' 'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'SafeNativeMemoryBufferHandle.PtrToStructure<T>(int)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'ShareInfo.ResourceType.get()' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' calls into 'Marshal.StructureToPtr(object, IntPtr, bool)' which has a LinkDemand. By making this call, 'Marshal.StructureToPtr(object, IntPtr, bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'SafeNativeMemoryBufferHandle.StructureToPtr(object, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'Marshal.Copy(IntPtr, byte[], int, int)' which has a LinkDemand. By making this call, 'Marshal.Copy(IntPtr, byte[], int, int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' 'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'SafeNativeMemoryBufferHandle.ToByteArray(int, int)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' 'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' ->'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' 'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' ->'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' 'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' ->'BackupFileStream.BackupFileStream(SafeFileHandle, FileSystemRights)' 'BackupFileStream.Flush()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.Flush()' ->'BackupFileStream.Flush()' 'BackupFileStream.GetAccessControl()' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.GetAccessControl()' ->'BackupFileStream.GetAccessControl()' 'BackupFileStream.GetAccessControl()' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.GetAccessControl()' ->'BackupFileStream.GetAccessControl()' 'BackupFileStream.Lock(long, long)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.Lock(long, long)' ->'BackupFileStream.Lock(long, long)' 'BackupFileStream.ReadStreamInfo()' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.ReadStreamInfo()' ->'BackupFileStream.ReadStreamInfo()' 'BackupFileStream.Skip(long)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.Skip(long)' ->'BackupFileStream.Skip(long)' 'BackupFileStream.Unlock(long, long)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'BackupFileStream.Unlock(long, long)' ->'BackupFileStream.Unlock(long, long)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.OffsetOf(Type, string)' which has a LinkDemand. By making this call, 'Marshal.OffsetOf(Type, string)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.OffsetOf(Type, string)' which has a LinkDemand. By making this call, 'Marshal.OffsetOf(Type, string)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.OffsetOf(Type, string)' which has a LinkDemand. By making this call, 'Marshal.OffsetOf(Type, string)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'Marshal.OffsetOf(Type, string)' which has a LinkDemand. By making this call, 'Marshal.OffsetOf(Type, string)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'Device.GetLinkTargetInfoCore(SafeFileHandle)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'Directory.GetCurrentDirectory()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.GetCurrentDirectory()' ->'Directory.GetCurrentDirectory()' 'Directory.SetCurrentDirectory(string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Directory.SetCurrentDirectory(string, PathFormat)' ->'Directory.SetCurrentDirectory(string, PathFormat)' 'DiskSpaceInfo.Refresh()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DiskSpaceInfo.Refresh()' ->'DiskSpaceInfo.Refresh()' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' 'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' 'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' 'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' 'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' 'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' 'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' 'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' 'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' 'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' 'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' 'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' 'File.GetEncryptionStatusCore(string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' 'File.GetEncryptionStatusCore(string, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' 'File.GetFileInfoByHandle(SafeFileHandle)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetFileInfoByHandle(SafeFileHandle)' ->'File.GetFileInfoByHandle(SafeFileHandle)' 'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' 'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' 'File.IsLockedCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetHRForException(Exception)' which has a LinkDemand. By making this call, 'Marshal.GetHRForException(Exception)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'File.IsLockedCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetHRForException(Exception)' which has a LinkDemand. By making this call, 'Marshal.GetHRForException(Exception)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'File.IsLockedCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetHRForException(Exception)' which has a LinkDemand. By making this call, 'Marshal.GetHRForException(Exception)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'File.IsLockedCore(KernelTransaction, string, PathFormat)' calls into 'Marshal.GetHRForException(Exception)' which has a LinkDemand. By making this call, 'Marshal.GetHRForException(Exception)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' calls into 'SafeHandle.Dispose()' which has a LinkDemand. By making this call, 'SafeHandle.Dispose()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'File.ReplaceCore(string, string, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' 'File.ReplaceCore(string, string, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' 'File.ReplaceCore(string, string, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' 'File.ReplaceCore(string, string, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' 'File.ReplaceCore(string, string, string, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' 'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' 'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' 'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Commit()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.GetExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.GetExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Rollback()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.GetHRForLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetHRForLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Commit()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.GetHRForLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetHRForLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Rollback()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Commit()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Rollback()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.ThrowExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.ThrowExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Commit()' 'KernelTransaction.CheckTransaction()' calls into 'Marshal.ThrowExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.ThrowExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.CheckTransaction()' ->'KernelTransaction.Rollback()' Review declarative security for 'NativeMethods.AssocCreate(Guid, ref Guid, out NativeMethods.IQueryAssociations)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocCreate(Guid, ref Guid, out NativeMethods.IQueryAssociations)' ->'Shell32Info.Initialize()' ->'Shell32Info.Refresh()' Review declarative security for 'NativeMethods.AssocCreate(Guid, ref Guid, out NativeMethods.IQueryAssociations)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocCreate(Guid, ref Guid, out NativeMethods.IQueryAssociations)' ->'Shell32Info.Initialize()' ->'Shell32Info.Shell32Info(string, PathFormat)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileAssociation(string)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileContentType(string)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileDefaultIcon(string)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileFriendlyAppName(string)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileFriendlyDocName(string)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileOpenWithAppName(string)' Review declarative security for 'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AssocQueryString(Shell32.AssociationAttributes, Shell32.AssociationString, string, string, StringBuilder, out uint)' ->'Shell32.GetFileAssociationCore(string, Shell32.AssociationAttributes, Shell32.AssociationString)' ->'Shell32.GetFileVerbCommand(string)' Review declarative security for 'NativeMethods.BackupRead(SafeFileHandle, SafeGlobalMemoryBufferHandle, uint, out uint, bool, bool, ref IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.BackupRead(SafeFileHandle, SafeGlobalMemoryBufferHandle, uint, out uint, bool, bool, ref IntPtr)' ->'BackupFileStream.Read(byte[], int, int, bool)' Review declarative security for 'NativeMethods.BackupRead(SafeFileHandle, SafeGlobalMemoryBufferHandle, uint, out uint, bool, bool, ref IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.BackupRead(SafeFileHandle, SafeGlobalMemoryBufferHandle, uint, out uint, bool, bool, ref IntPtr)' ->'BackupFileStream.ReadStreamInfo()' Review declarative security for 'NativeMethods.BackupSeek(SafeFileHandle, uint, uint, out uint, out uint, ref IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.BackupSeek(SafeFileHandle, uint, uint, out uint, out uint, ref IntPtr)' ->'BackupFileStream.Skip(long)' Review declarative security for 'NativeMethods.BackupWrite(SafeFileHandle, SafeGlobalMemoryBufferHandle, uint, out uint, bool, bool, ref IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.BackupWrite(SafeFileHandle, SafeGlobalMemoryBufferHandle, uint, out uint, bool, bool, ref IntPtr)' ->'BackupFileStream.Write(byte[], int, int, bool)' Review declarative security for 'NativeMethods.CommitTransaction(SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CommitTransaction(SafeHandle)' ->'KernelTransaction.Commit()' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileEx(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CopyFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, out bool, CopyOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectory(string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryEx(string, string, NativeMethods.SecurityAttributes)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateDirectoryTransacted(string, string, NativeMethods.SecurityAttributes, SafeHandle)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFile(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.CreateFileMapping(SafeFileHandle, SafeHandle, uint, uint, uint, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileMapping(SafeFileHandle, SafeHandle, uint, uint, uint, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFileMapping(SafeFileHandle, SafeHandle, uint, uint, uint, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileMapping(SafeFileHandle, SafeHandle, uint, uint, uint, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateFileTransacted(string, FileSystemRights, FileShare, NativeMethods.SecurityAttributes, FileMode, ExtendedFileAttributes, IntPtr, SafeHandle, IntPtr, IntPtr)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.CreateHardLink(string, string, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLink(string, string, IntPtr)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' Review declarative security for 'NativeMethods.CreateHardLink(string, string, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLink(string, string, IntPtr)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateHardLink(string, string, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLink(string, string, IntPtr)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateHardLink(string, string, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLink(string, string, IntPtr)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' Review declarative security for 'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateHardLinkTransacted(string, string, IntPtr, SafeHandle)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLink(string, string, SymbolicLinkTarget)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateSymbolicLinkTransacted(string, string, SymbolicLinkTarget, SafeHandle)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.CreateTransaction(NativeMethods.SecurityAttributes, IntPtr, uint, uint, uint, int, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.CreateTransaction(NativeMethods.SecurityAttributes, IntPtr, uint, uint, uint, int, string)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.DecryptFile(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DecryptFile(string, uint)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string)' Review declarative security for 'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string, DosDeviceAttributes)' Review declarative security for 'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string)' Review declarative security for 'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string)' Review declarative security for 'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, DosDeviceAttributes, bool)' Review declarative security for 'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DefineDosDevice(DosDeviceAttributes, string, string)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.DeleteFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFile(string)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.DeleteFileTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteFileTransacted(string, SafeHandle)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.DeleteVolumeMountPoint(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeleteVolumeMountPoint(string)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPoint(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, IntPtr, uint, SafeGlobalMemoryBufferHandle, uint, out uint, IntPtr)' ->'Device.GetLinkTargetInfoCore(SafeFileHandle)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.DeviceIoControl(SafeFileHandle, uint, object, uint, object, uint, out uint, IntPtr)' ->'Device.InvokeIoControlUnknownSize<TV>(SafeFileHandle, uint, TV, uint)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.EncryptFile(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptFile(string)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.EncryptionDisable(string, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptionDisable(string, bool)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' Review declarative security for 'NativeMethods.EncryptionDisable(string, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptionDisable(string, bool)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.EncryptionDisable(string, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptionDisable(string, bool)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' Review declarative security for 'NativeMethods.EncryptionDisable(string, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptionDisable(string, bool)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.EncryptionDisable(string, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptionDisable(string, bool)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' Review declarative security for 'NativeMethods.EncryptionDisable(string, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.EncryptionDisable(string, bool)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' Review declarative security for 'NativeMethods.FileEncryptionStatus(string, out FileEncryptionStatus)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FileEncryptionStatus(string, out FileEncryptionStatus)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' Review declarative security for 'NativeMethods.FileEncryptionStatus(string, out FileEncryptionStatus)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FileEncryptionStatus(string, out FileEncryptionStatus)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileEx(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FindFirstFileTransacted(string, NativeMethods.FINDEX_INFO_LEVELS, out NativeMethods.WIN32_FIND_DATA, NativeMethods.FINDEX_SEARCH_OPS, IntPtr, NativeMethods.FindExAdditionalFlags, SafeHandle)' ->'FindFileSystemEntryInfo.FindFirstFile(string, out NativeMethods.WIN32_FIND_DATA)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' Review declarative security for 'NativeMethods.FlushFileBuffers(SafeFileHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.FlushFileBuffers(SafeFileHandle)' ->'BackupFileStream.Flush()' Review declarative security for 'NativeMethods.GetCompressedFileSize(string, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSize(string, out uint)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' Review declarative security for 'NativeMethods.GetCompressedFileSize(string, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSize(string, out uint)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetCompressedFileSize(string, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSize(string, out uint)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetCompressedFileSize(string, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSize(string, out uint)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' Review declarative security for 'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCompressedFileSizeTransacted(string, out uint, SafeHandle)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetCurrentDirectory(uint, StringBuilder)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetCurrentDirectory(uint, StringBuilder)' ->'Directory.GetCurrentDirectory()' Review declarative security for 'NativeMethods.GetDiskFreeSpace(string, out int, out int, out int, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetDiskFreeSpace(string, out int, out int, out int, out uint)' ->'DiskSpaceInfo.Refresh()' Review declarative security for 'NativeMethods.GetDiskFreeSpaceEx(string, out long, out long, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetDiskFreeSpaceEx(string, out long, out long, out long)' ->'DiskSpaceInfo.Refresh()' Review declarative security for 'NativeMethods.GetDriveType(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetDriveType(string)' ->'Volume.GetDriveType(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesEx(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileAttributesTransacted(string, NativeMethods.GetFileExInfoLevels, out NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, SafeHandle)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' Review declarative security for 'NativeMethods.GetFileInformationByHandle(SafeFileHandle, out NativeMethods.BY_HANDLE_FILE_INFORMATION)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandle(SafeFileHandle, out NativeMethods.BY_HANDLE_FILE_INFORMATION)' ->'File.GetFileInfoByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileInformationByHandleEx_FileBasicInfo(SafeFileHandle, NativeMethods.FileInfoByHandleClass, out NativeMethods.FILE_BASIC_INFO, uint)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFileSizeEx(SafeFileHandle, out long)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.GetFinalPathNameByHandle(SafeFileHandle, StringBuilder, uint, FinalPathFormats)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFinalPathNameByHandle(SafeFileHandle, StringBuilder, uint, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFinalPathNameByHandle(SafeFileHandle, StringBuilder, uint, FinalPathFormats)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFinalPathNameByHandle(SafeFileHandle, StringBuilder, uint, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryName(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRoot(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.SetCurrentDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'DirectoryInfo.DirectoryInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'FileInfo.FileInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Shell32Info.Shell32Info(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string, GetFullPathOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string, GetFullPathOptions)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Shell32.PathFileExists(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumePathName(string)' Review declarative security for 'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathName(string, uint, StringBuilder, IntPtr)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryName(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRoot(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.SetCurrentDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'DirectoryInfo.DirectoryInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'FileInfo.FileInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string, SearchOption)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Shell32Info.Shell32Info(string, PathFormat)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string, GetFullPathOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string, GetFullPathOptions)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Shell32.PathFileExists(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumePathName(string)' Review declarative security for 'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetFullPathNameTransacted(string, uint, StringBuilder, IntPtr, SafeHandle)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.GetLongPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.GetLongPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetLongPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.GetLongPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetLongPathNameTransacted(string, StringBuilder, uint, SafeHandle)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetMappedFileName(IntPtr, SafeLocalMemoryBufferHandle, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetMappedFileName(IntPtr, SafeLocalMemoryBufferHandle, StringBuilder, uint)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.GetMappedFileName(IntPtr, SafeLocalMemoryBufferHandle, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetMappedFileName(IntPtr, SafeLocalMemoryBufferHandle, StringBuilder, uint)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.GetShortPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetShortPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.GetShortPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetShortPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetShortPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetShortPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.GetShortPathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetShortPathName(string, StringBuilder, uint)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.GetVolumeInformation(string, StringBuilder, uint, out uint, out int, out NativeMethods.VolumeInfoAttributes, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetVolumeInformation(string, StringBuilder, uint, out uint, out int, out NativeMethods.VolumeInfoAttributes, StringBuilder, uint)' ->'VolumeInfo.Refresh()' Review declarative security for 'NativeMethods.GetVolumeInformationByHandle(SafeFileHandle, StringBuilder, uint, out uint, out int, out NativeMethods.VolumeInfoAttributes, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetVolumeInformationByHandle(SafeFileHandle, StringBuilder, uint, out uint, out int, out NativeMethods.VolumeInfoAttributes, StringBuilder, uint)' ->'VolumeInfo.Refresh()' Review declarative security for 'NativeMethods.GetVolumeNameForVolumeMountPoint(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetVolumeNameForVolumeMountPoint(string, StringBuilder, uint)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.GetVolumePathName(string, StringBuilder, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetVolumePathName(string, StringBuilder, uint)' ->'Volume.GetVolumePathName(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetFileInfoByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetFileInfoByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetFileInfoByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.IsClosed.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsClosed.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'NativeMethods.IsValidHandle(SafeHandle, int, bool)' calls into 'SafeHandle.IsInvalid.get()' which has a LinkDemand. By making this call, 'SafeHandle.IsInvalid.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'NativeMethods.IsValidHandle(SafeHandle, int, bool)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.LockFile(SafeFileHandle, uint, uint, uint, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.LockFile(SafeFileHandle, uint, uint, uint, uint)' ->'BackupFileStream.Lock(long, long)' Review declarative security for 'NativeMethods.MapViewOfFile(SafeFileHandle, uint, uint, uint, UIntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MapViewOfFile(SafeFileHandle, uint, uint, uint, UIntPtr)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.MapViewOfFile(SafeFileHandle, uint, uint, uint, UIntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MapViewOfFile(SafeFileHandle, uint, uint, uint, UIntPtr)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileTransacted(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions, SafeHandle)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.MoveFileWithProgress(string, string, NativeMethods.NativeCopyMoveProgressRoutine, IntPtr, MoveOptions)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.OpenEncryptedFileRaw(string, NativeMethods.EncryptedFileRawMode, out SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.PathFileExists(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.PathFileExists(string)' ->'Shell32.PathFileExists(string)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReadEncryptedFileRaw(NativeMethods.EncryptedFileRawExportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.RemoveDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectory(string)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RemoveDirectoryTransacted(string, SafeHandle)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' Review declarative security for 'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' Review declarative security for 'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ReplaceFile(string, string, string, FileSystemRights, IntPtr, IntPtr)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.RollbackTransaction(SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.RollbackTransaction(SafeHandle)' ->'KernelTransaction.Rollback()' Review declarative security for 'NativeMethods.SetCurrentDirectory(string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetCurrentDirectory(string)' ->'Directory.SetCurrentDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'DiskSpaceInfo.Refresh()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryName(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRoot(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.SetCurrentDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'DirectoryInfo.DirectoryInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'FileInfo.FileInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles()' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string, SearchOption)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Shell32Info.Shell32Info(string, PathFormat)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string, GetFullPathOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string, GetFullPathOptions)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Shell32.PathFileExists(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumePathName(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string, DosDeviceAttributes)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, DosDeviceAttributes, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, bool)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPoint(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.GetDriveType(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.GetVolumePathName(string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.SetVolumeLabel(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetErrorMode(NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'VolumeInfo.Refresh()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributes(string, FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributes(string, FileAttributes)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileAttributesTransacted(string, FileAttributes, SafeHandle)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetFileTime(SafeFileHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle, SafeGlobalMemoryBufferHandle)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'DiskSpaceInfo.Refresh()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.Delete(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'File.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.DeleteFileCore(KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Delete(bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Directory.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'DriveInfo.IsReady.get()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.Exists(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'File.ExistsTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.ExistsCore(bool, KernelTransaction, string, PathFormat)' ->'Volume.IsReady(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributes(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetAttributesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetCreationTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetCreationTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastAccessTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastAccessTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'Directory.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.GetLastWriteTimeCore(KernelTransaction, string, bool, PathFormat)' ->'File.GetLastWriteTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'File.GetAttributesExCore<T>(KernelTransaction, string, PathFormat, bool)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'File.FillAttributeInfoCore(KernelTransaction, string, ref NativeMethods.WIN32_FILE_ATTRIBUTE_DATA, bool, bool)' ->'FileSystemInfo.Refresh()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfo(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.GetFileSystemEntryInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'FindFileSystemEntryInfo.Get<T>()' ->'File.GetFileSystemEntryInfoCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileSystemInfo.RefreshEntryInfo()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.DisableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'Directory.EnableEncryption(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.DisableEncryption()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EnableDisableEncryptionCore(string, bool, PathFormat)' ->'DirectoryInfo.EnableEncryption()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Decrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'Directory.Encrypt(string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Decrypt(bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.EncryptDecryptDirectoryCore(string, bool, bool, PathFormat)' ->'DirectoryInfo.Encrypt(bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRoot(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetDirectoryRootCore(KernelTransaction, string, PathFormat)' ->'Directory.GetDirectoryRootTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParent(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Directory.GetParentTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryName(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRoot(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetParentCore(KernelTransaction, string, PathFormat)' ->'Path.GetSuffixedDirectoryNameWithoutRootCore(KernelTransaction, string)' ->'Path.GetSuffixedDirectoryNameWithoutRootTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetProperties(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.GetPropertiesCore(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetPropertiesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Directory.SetCurrentDirectory(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlink(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateHardlinkCore(KernelTransaction, string, string, PathFormat)' ->'File.CreateHardlinkTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLink(string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.CreateSymbolicLinkCore(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' ->'File.CreateSymbolicLinkTransacted(KernelTransaction, string, string, SymbolicLinkTarget, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Decrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'File.Encrypt(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Decrypt()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.EncryptDecryptFileCore(bool, string, bool, PathFormat)' ->'FileInfo.Encrypt()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSize(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetCompressedSizeCore(KernelTransaction, string, PathFormat)' ->'File.GetCompressedSizeTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.GetEncryptionStatusCore(string, PathFormat)' ->'File.GetEncryptionStatus(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'File.Replace(string, string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.ReplaceCore(string, string, string, bool, PathFormat)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributes(string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'File.SetAttributesTransacted(KernelTransaction, string, FileAttributes, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'File.SetAttributesCore(bool, KernelTransaction, string, FileAttributes, bool, PathFormat)' ->'FileSystemInfo.Attributes.set(FileAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileInfo.Replace(string, string, bool, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'DirectoryInfo.DirectoryInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FileSystemInfo.InitializeCore(bool, KernelTransaction, string, PathFormat)' ->'FileInfo.FileInfo(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjects(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.CountFileSystemObjectsTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectories(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateDirectoriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntries(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfos<T>(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosTransacted<T>(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFiles(string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.EnumerateFilesTransacted(KernelTransaction, string, string, SearchOption, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectories(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetDirectoriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntries(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFileSystemEntriesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFiles(string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'Directory.GetFilesTransacted(KernelTransaction, string, string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.CountFileSystemObjects(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, DirectoryEnumerationOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.EnumerateFiles(string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetDirectories(string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFileSystemInfos(string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles()' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'FindFileSystemEntryInfo.FindFileSystemEntryInfo(bool, KernelTransaction, string, string, DirectoryEnumerationOptions, Type, PathFormat)' ->'Directory.EnumerateFileSystemEntryInfosCore<T>(KernelTransaction, string, string, DirectoryEnumerationOptions, PathFormat)' ->'DirectoryInfo.GetFiles(string, SearchOption)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetExtendedLengthPathCore(KernelTransaction, string, PathFormat, GetFullPathOptions)' ->'Shell32Info.Shell32Info(string, PathFormat)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPath(string, GetFullPathOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTackleCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetFullPathTransacted(KernelTransaction, string, GetFullPathOptions)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPath(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetLongFrom83ShortPathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83Path(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.GetLongShort83PathCore(KernelTransaction, string, bool)' ->'Path.GetShort83PathTransacted(KernelTransaction, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Shell32.PathFileExists(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.GetVolumePathName(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Path.GetFullPathCore(KernelTransaction, string, GetFullPathOptions)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DefineDosDevice(string, string, DosDeviceAttributes)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, DosDeviceAttributes, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DefineDosDeviceCore(bool, string, string, DosDeviceAttributes, bool)' ->'Volume.DeleteDosDevice(string, string, bool)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPoint(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.GetDriveType(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.GetVolumeGuid(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.GetVolumePathName(string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.SetVolumeLabel(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetThreadErrorMode(NativeMethods.ErrorMode, out NativeMethods.ErrorMode)' ->'NativeMethods.ChangeErrorMode.ChangeErrorMode(NativeMethods.ErrorMode)' ->'VolumeInfo.Refresh()' Review declarative security for 'NativeMethods.SetVolumeLabel(string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetVolumeLabel(string, string)' ->'Volume.SetCurrentVolumeLabel(string)' Review declarative security for 'NativeMethods.SetVolumeLabel(string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetVolumeLabel(string, string)' ->'Volume.SetVolumeLabel(string, string)' Review declarative security for 'NativeMethods.SetVolumeMountPoint(string, string)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetVolumeMountPoint(string, string)' ->'Volume.SetVolumeMountPoint(string, string)' Review declarative security for 'NativeMethods.ShGetFileInfo(string, FileAttributes, out Shell32.FileInfo, uint, Shell32.FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ShGetFileInfo(string, FileAttributes, out Shell32.FileInfo, uint, Shell32.FileAttributes)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileIcon(string, Shell32.FileAttributes)' Review declarative security for 'NativeMethods.ShGetFileInfo(string, FileAttributes, out Shell32.FileInfo, uint, Shell32.FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ShGetFileInfo(string, FileAttributes, out Shell32.FileInfo, uint, Shell32.FileAttributes)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfo(string, FileAttributes, Shell32.FileAttributes, bool)' Review declarative security for 'NativeMethods.ShGetFileInfo(string, FileAttributes, out Shell32.FileInfo, uint, Shell32.FileAttributes)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.ShGetFileInfo(string, FileAttributes, out Shell32.FileInfo, uint, Shell32.FileAttributes)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32Info.Attributes.get()' Review declarative security for 'NativeMethods.UnlockFile(SafeFileHandle, uint, uint, uint, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.UnlockFile(SafeFileHandle, uint, uint, uint, uint)' ->'BackupFileStream.Unlock(long, long)' Review declarative security for 'NativeMethods.UnmapViewOfFile(SafeLocalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.UnmapViewOfFile(SafeLocalMemoryBufferHandle)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' Review declarative security for 'NativeMethods.UnmapViewOfFile(SafeLocalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.UnmapViewOfFile(SafeLocalMemoryBufferHandle)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ExportEncryptedDirectoryRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'Directory.ImportEncryptedDirectoryRaw(Stream, string, bool, PathFormat)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ExportEncryptedFileRaw(string, Stream, PathFormat)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, PathFormat)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool)' Review declarative security for 'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WriteEncryptedFileRaw(NativeMethods.EncryptedFileRawImportCallback, IntPtr, SafeEncryptedFileRawHandle)' ->'File.ImportExportEncryptedFileDirectoryRawCore(bool, bool, Stream, string, PathFormat, bool)' ->'File.ImportEncryptedFileRaw(Stream, string, bool, PathFormat)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.GetCurrentProcess()' which has a LinkDemand. By making this call, 'Process.GetCurrentProcess()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.GetCurrentProcess()' which has a LinkDemand. By making this call, 'Process.GetCurrentProcess()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.Handle.get()' which has a LinkDemand. By making this call, 'Process.Handle.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle)' 'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' calls into 'Process.Handle.get()' which has a LinkDemand. By making this call, 'Process.Handle.get()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandleCore(SafeFileHandle, FinalPathFormats)' ->'Path.GetFinalPathNameByHandle(SafeFileHandle, FinalPathFormats)' 'Path.NormalizePath(string, GetFullPathOptions)' has 71 local variables, 47 of which were generated by the compiler. Refactor 'Path.NormalizePath(string, GetFullPathOptions)' so that it uses fewer than 64 local variables. 'SafeFindFileHandle.SafeFindFileHandle(IntPtr, bool)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeFindFileHandle.SafeFindFileHandle(IntPtr, bool)' ->'SafeFindFileHandle.SafeFindFileHandle(IntPtr, bool)' 'SafeFindFileHandle.SafeFindFileHandle(IntPtr, bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeFindFileHandle.SafeFindFileHandle(IntPtr, bool)' ->'SafeFindFileHandle.SafeFindFileHandle(IntPtr, bool)' 'SafeFindVolumeHandle.SafeFindVolumeHandle(IntPtr, bool)' calls into 'SafeHandle.SetHandle(IntPtr)' which has a LinkDemand. By making this call, 'SafeHandle.SetHandle(IntPtr)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeFindVolumeHandle.SafeFindVolumeHandle(IntPtr, bool)' ->'SafeFindVolumeHandle.SafeFindVolumeHandle(IntPtr, bool)' 'SafeFindVolumeHandle.SafeFindVolumeHandle(IntPtr, bool)' calls into 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' which has a LinkDemand. By making this call, 'SafeHandleZeroOrMinusOneIsInvalid.SafeHandleZeroOrMinusOneIsInvalid(bool)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'SafeFindVolumeHandle.SafeFindVolumeHandle(IntPtr, bool)' ->'SafeFindVolumeHandle.SafeFindVolumeHandle(IntPtr, bool)' 'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileIcon(string, Shell32.FileAttributes)' 'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfo(string, FileAttributes, Shell32.FileAttributes, bool)' 'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32Info.Attributes.get()' 'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileIcon(string, Shell32.FileAttributes)' 'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfo(string, FileAttributes, Shell32.FileAttributes, bool)' 'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32.GetFileInfoCore(string, FileAttributes, Shell32.FileAttributes, bool, bool)' ->'Shell32Info.Attributes.get()' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.Delete(string, bool, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectories(string, bool, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories()' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteEmptySubdirectoriesCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, PathFormat)' ->'DirectoryInfo.DeleteEmptySubdirectories(bool, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'Directory.DeleteTransacted(KernelTransaction, string, bool, bool, PathFormat)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete()' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Directory.DeleteDirectoryCore(FileSystemEntryInfo, KernelTransaction, string, bool, bool, bool, bool, PathFormat)' ->'DirectoryInfo.Delete(bool, bool)' 'Volume.DeleteVolumeMountPointCore(string, bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPointCore(string, bool)' ->'Volume.DeleteVolumeMountPoint(string)' 'Volume.GetVolumeGuid(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.GetVolumeGuid(string)' ->'Volume.GetVolumeGuid(string)' 'Volume.GetVolumePathName(string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.GetVolumePathName(string)' ->'Volume.GetVolumePathName(string)' 'Volume.SetCurrentVolumeLabel(string)' calls into 'Marshal.GetHRForLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetHRForLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.SetCurrentVolumeLabel(string)' ->'Volume.SetCurrentVolumeLabel(string)' 'Volume.SetCurrentVolumeLabel(string)' calls into 'Marshal.ThrowExceptionForHR(int)' which has a LinkDemand. By making this call, 'Marshal.ThrowExceptionForHR(int)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.SetCurrentVolumeLabel(string)' ->'Volume.SetCurrentVolumeLabel(string)' 'Volume.SetVolumeMountPoint(string, string)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Volume.SetVolumeMountPoint(string, string)' ->'Volume.SetVolumeMountPoint(string, string)' 'VolumeInfo.Refresh()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'VolumeInfo.Refresh()' ->'VolumeInfo.Refresh()' 'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string)' 'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string, string, string)' 'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' calls into 'Marshal.PtrToStructure(IntPtr, Type)' which has a LinkDemand. By making this call, 'Marshal.PtrToStructure(IntPtr, Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsInfo(string)' 'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string)' 'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string, string, string)' 'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' calls into 'Marshal.SizeOf(Type)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(Type)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'DfsInfo.DfsInfo(NativeMethods.DFS_INFO_9)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsInfo(string)' Review declarative security for 'NativeMethods.NetDfsGetClientInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetDfsGetClientInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string)' Review declarative security for 'NativeMethods.NetDfsGetClientInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetDfsGetClientInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string, string, string)' Review declarative security for 'NativeMethods.NetDfsGetClientInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetDfsGetClientInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsInfo(string)' Review declarative security for 'NativeMethods.NetDfsGetInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetDfsGetInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string)' Review declarative security for 'NativeMethods.NetDfsGetInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetDfsGetInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsClientInfo(string, string, string)' Review declarative security for 'NativeMethods.NetDfsGetInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetDfsGetInfo(string, string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetDfsInfoCore(bool, string, string, string)' ->'Host.GetDfsInfo(string)' Review declarative security for 'NativeMethods.NetFileClose(string, uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetFileClose(string, uint)' ->'OpenResourceInfo.Close()' Review declarative security for 'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(ShareInfoLevel, string, bool)' Review declarative security for 'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(ShareInfoLevel, string, string, bool)' Review declarative security for 'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(string, bool)' Review declarative security for 'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'Host.GetShareInfo(string, string, bool)' Review declarative security for 'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.NetShareGetInfo(string, string, uint, out SafeGlobalMemoryBufferHandle)' ->'Host.GetShareInfoCore(ShareInfoLevel, string, string, bool)' ->'ShareInfo.ResourceType.get()' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.Dispose(bool)' ->'DriveConnection.Dispose()' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.Dispose(bool)' ->'DriveConnection.~DriveConnection()' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.DriveConnection(string)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.DriveConnection(string, NetworkCredential, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.DriveConnection(string, string, string, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(IntPtr, string, string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(IntPtr, string, string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(string, string)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(string, string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(string, string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(IntPtr, string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(IntPtr, string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(string)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectDrive(string)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectDrive(string, bool, bool)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectFrom(string)' Review declarative security for 'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetCancelConnection(string, NativeMethods.Connect, bool)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectFrom(string, bool, bool)' Review declarative security for 'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedConnectionName(string)' Review declarative security for 'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.GetMappedUncName(string)' Review declarative security for 'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string)' Review declarative security for 'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool)' Review declarative security for 'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetGetUniversalName(string, uint, SafeGlobalMemoryBufferHandle, out uint)' ->'Host.GetRemoteNameInfoCore(string, bool)' ->'Path.LocalToUncCore(string, bool, bool, bool)' ->'Path.LocalToUnc(string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.Dispose(bool)' ->'DriveConnection.Dispose()' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.Dispose(bool)' ->'DriveConnection.~DriveConnection()' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.DriveConnection(string)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.DriveConnection(string, NetworkCredential, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'DriveConnection.DriveConnection(string, string, string, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(IntPtr, string, string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(IntPtr, string, string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(string, string)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(string, string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectDrive(string, string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(IntPtr, string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(IntPtr, string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(string)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(string, NetworkCredential, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.ConnectTo(string, string, string, bool, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectDrive(string)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectDrive(string, bool, bool)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectFrom(string)' Review declarative security for 'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.WNetUseConnection(IntPtr, ref NativeMethods.NETRESOURCE, string, string, NativeMethods.Connect, StringBuilder, out uint, out uint)' ->'Host.ConnectDisconnectCore(Host.ConnectDisconnectArguments)' ->'Host.DisconnectFrom(string, bool, bool)' 'InternalPrivilegeEnabler.AdjustPrivilege(bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.Dispose()' ->'PrivilegeEnabler.Dispose()' 'InternalPrivilegeEnabler.AdjustPrivilege(bool)' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.InternalPrivilegeEnabler(Privilege)' ->'PrivilegeEnabler.PrivilegeEnabler(Privilege, params Privilege[])' 'InternalPrivilegeEnabler.AdjustPrivilege(bool)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.Dispose()' ->'PrivilegeEnabler.Dispose()' 'InternalPrivilegeEnabler.AdjustPrivilege(bool)' calls into 'Marshal.SizeOf(object)' which has a LinkDemand. By making this call, 'Marshal.SizeOf(object)' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.InternalPrivilegeEnabler(Privilege)' ->'PrivilegeEnabler.PrivilegeEnabler(Privilege, params Privilege[])' Review declarative security for 'NativeMethods.AdjustTokenPrivileges(IntPtr, bool, ref TokenPrivileges, uint, out TokenPrivileges, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AdjustTokenPrivileges(IntPtr, bool, ref TokenPrivileges, uint, out TokenPrivileges, out uint)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.Dispose()' ->'PrivilegeEnabler.Dispose()' Review declarative security for 'NativeMethods.AdjustTokenPrivileges(IntPtr, bool, ref TokenPrivileges, uint, out TokenPrivileges, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.AdjustTokenPrivileges(IntPtr, bool, ref TokenPrivileges, uint, out TokenPrivileges, out uint)' ->'InternalPrivilegeEnabler.AdjustPrivilege(bool)' ->'InternalPrivilegeEnabler.InternalPrivilegeEnabler(Privilege)' ->'PrivilegeEnabler.PrivilegeEnabler(Privilege, params Privilege[])' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetNamedSecurityInfo(string, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorControl(SafeGlobalMemoryBufferHandle, out SecurityDescriptorControl, out uint)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorDacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorGroup(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'BackupFileStream.GetAccessControl()' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' Review declarative security for 'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorLength(SafeGlobalMemoryBufferHandle)' ->'File.GetSecurityDescriptor<T>(uint, bool, string, SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorOwner(SafeGlobalMemoryBufferHandle, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityDescriptorSacl(SafeGlobalMemoryBufferHandle, out bool, out IntPtr, out bool)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'BackupFileStream.GetAccessControl()' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'Directory.GetAccessControl(SafeFileHandle, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControl(SafeFileHandle, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' Review declarative security for 'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.GetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, out IntPtr, out IntPtr, out IntPtr, out IntPtr, out SafeGlobalMemoryBufferHandle)' ->'File.GetAccessControlHandleCore<T>(bool, bool, SafeFileHandle, AccessControlSections, SecurityInformation)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' Review declarative security for 'NativeMethods.LookupPrivilegeDisplayName(string, string, ref StringBuilder, ref uint, out uint)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.LookupPrivilegeDisplayName(string, string, ref StringBuilder, ref uint, out uint)' ->'Privilege.LookupDisplayName()' Review declarative security for 'NativeMethods.LookupPrivilegeValue(string, string, out Luid)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.LookupPrivilegeValue(string, string, out Luid)' ->'Privilege.LookupLuid()' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetNamedSecurityInfo(string, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'BackupFileStream.SetAccessControl(ObjectSecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(SafeFileHandle, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'Directory.SetAccessControl(string, DirectorySecurity, PathFormat)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'DirectoryInfo.SetAccessControl(DirectorySecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(SafeFileHandle, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, AccessControlSections, PathFormat)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'File.SetAccessControl(string, FileSecurity, PathFormat)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity)' Review declarative security for 'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: ->'NativeMethods.SetSecurityInfo(SafeHandle, ObjectType, SecurityInformation, IntPtr, IntPtr, IntPtr, IntPtr)' ->'File.SetAccessControlCore(string, SafeFileHandle, ObjectSecurity, AccessControlSections, PathFormat)' ->'FileInfo.SetAccessControl(FileSecurity, AccessControlSections)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, CopyOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Copy(string, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, MoveOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.Move(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'Directory.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, CopyOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.CopyTo(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, MoveOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CopyMoveCore(KernelTransaction, string, string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'DirectoryInfo.CopyToMoveToCore(string, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'DirectoryInfo.MoveTo(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, DirectorySecurity, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, DirectorySecurity, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectory(string, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, DirectorySecurity, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, DirectorySecurity, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'Directory.CreateDirectoryTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.Create(bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, DirectorySecurity, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'Directory.CreateDirectoryCore(KernelTransaction, string, string, ObjectSecurity, bool, PathFormat)' ->'DirectoryInfo.CreateSubdirectoryCore(string, string, DirectorySecurity, bool)' ->'DirectoryInfo.CreateSubdirectory(string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'BackupFileStream.BackupFileStream(string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, DirectoryEnumerationOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Compress(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.CompressTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, DirectoryEnumerationOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.Decompress(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, DirectoryEnumerationOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'Directory.DecompressTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Compress(DirectoryEnumerationOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.CompressDecompressCore(KernelTransaction, string, string, DirectoryEnumerationOptions, bool, PathFormat)' ->'DirectoryInfo.Decompress(DirectoryEnumerationOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompression(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.DisableCompressionTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompression(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'Directory.EnableCompressionTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.DisableCompression()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'DirectoryInfo.EnableCompression()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Compress(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.CompressTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.Decompress(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'File.DecompressTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Compress()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'Device.ToggleCompressionCore(bool, KernelTransaction, string, bool, PathFormat)' ->'FileInfo.Decompress()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, CopyOptions, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Copy(string, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, CopyOptions, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.CopyTransacted(KernelTransaction, string, string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, MoveOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.Move(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, MoveOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'File.MoveTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, CopyOptions, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.CopyTo(string, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, CopyMoveProgressRoutine, object, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, MoveOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CopyMoveCore(bool, KernelTransaction, string, string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, CopyMoveResult, PathFormat)' ->'FileInfo.CopyToMoveToCore(string, bool, CopyOptions?, MoveOptions?, CopyMoveProgressRoutine, object, out string, PathFormat)' ->'FileInfo.MoveTo(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, FileSecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, FileOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.Create(string, int, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateText(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.CreateTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, FileSecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, FileOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'File.CreateTransacted(KernelTransaction, string, int, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.Create()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.CreateFileStreamCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileAccess, FileShare, int, PathFormat)' ->'FileInfo.CreateText()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.GetAccessControl(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'Directory.HasInheritedPermissions(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'DirectoryInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, AccessControlSections, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'File.GetAccessControl(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetAccessControlCore<T>(bool, string, AccessControlSections, PathFormat)' ->'FileInfo.GetAccessControl(AccessControlSections)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(SafeFileHandle)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTime(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'Directory.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(SafeFileHandle)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTime(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(SafeFileHandle)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtc(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetChangeTimeCore(bool, KernelTransaction, SafeFileHandle, string, bool, PathFormat)' ->'File.GetChangeTimeUtcTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfo(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetLinkTargetInfoCore(KernelTransaction, string, PathFormat)' ->'File.GetLinkTargetInfoTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(SafeFileHandle)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSize(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.GetSizeCore(KernelTransaction, SafeFileHandle, string, PathFormat)' ->'File.GetSizeTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupRead(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenBackupReadTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendText(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.AppendTextTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.AppendTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'FileInfo.AppendText(Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(KernelTransaction, string, HashType, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'File.GetHash(string, HashType, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.GetHashCore(KernelTransaction, string, HashType, PathFormat)' ->'FileInfo.GetHash(HashType)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLocked(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.IsLockedCore(KernelTransaction, string, PathFormat)' ->'File.IsLockedTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, FileAccess, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.Open(string, FileMode, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, FileOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, FileShare, int, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileAccess, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllText(string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.ReadAllTextCore(KernelTransaction, string, Encoding, PathFormat)' ->'File.ReadAllTextTransacted(KernelTransaction, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[])' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytes(string, byte[], PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[])' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAllBytesCore(KernelTransaction, string, byte[], PathFormat)' ->'File.WriteAllBytesTransacted(KernelTransaction, string, byte[], PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileAccess, FileShare)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenRead()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenText(Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileAccess, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.OpenWrite()' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, FileSecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, ExtendedFileAttributes, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, FileSecurity, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.OpenTransacted(KernelTransaction, string, FileMode, FileSystemRights, FileShare, int, FileOptions, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLines(string, IEnumerable<string>, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllText(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.AppendAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, IEnumerable<string>, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[])' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLines(string, string[], PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, IEnumerable<string>, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[])' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllLinesTransacted(KernelTransaction, string, string[], PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllText(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, Encoding, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'File.WriteAppendAllLinesCore(KernelTransaction, string, IEnumerable<string>, Encoding, bool, bool, PathFormat)' ->'File.WriteAllTextTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.OpenCore(KernelTransaction, string, FileMode, FileSystemRights, FileShare, ExtendedFileAttributes, int?, FileSecurity, PathFormat)' ->'FileInfo.Open(FileMode, FileSystemRights, FileShare)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTime(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'Directory.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTime(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtc(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetCreationTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTime(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtc(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastAccessTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTime(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtc(string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetLastWriteTimeUtcTransacted(KernelTransaction, string, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestamps(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtc(string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.SetTimestampsUtcTransacted(KernelTransaction, string, DateTime, DateTime, DateTime, bool, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestamps(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'Directory.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestamps(string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'File.TransferTimestampsCore(bool, KernelTransaction, string, string, PathFormat)' ->'File.TransferTimestampsTransacted(KernelTransaction, string, string, PathFormat)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.CreationTimeUtc.set(DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastAccessTimeUtc.set(DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'File.CreateFileCore(KernelTransaction, string, ExtendedFileAttributes, FileSecurity, FileMode, FileSystemRights, FileShare, bool, PathFormat)' ->'File.SetFsoDateTimeCore(bool, KernelTransaction, string, DateTime?, DateTime?, DateTime?, bool, PathFormat)' ->'FileSystemInfo.LastWriteTimeUtc.set(DateTime)' 'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' calls into 'SafeHandle.Close()' which has a LinkDemand. By making this call, 'SafeHandle.Close()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.ToUnmanagedSecurityAttributes(ObjectSecurity)' ->'NativeMethods.SecurityAttributes.SecurityAttributes(ObjectSecurity)' ->'KernelTransaction.KernelTransaction(ObjectSecurity, int, string)' 'Privilege.LookupDisplayName()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Privilege.LookupDisplayName()' ->'Privilege.LookupDisplayName()' 'Privilege.LookupLuid()' calls into 'Marshal.GetLastWin32Error()' which has a LinkDemand. By making this call, 'Marshal.GetLastWin32Error()' is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: ->'Privilege.LookupLuid()' ->'Privilege.LookupLuid()' Assemblies should have valid strong names Either the assembly has no strong name, an invalid one, or the strong name is valid only because of the computer configuration. The assembly should not be deployed in this state. The most common causes of this are: 1) The assembly's contents were modified after it was signed. 2) The signing process failed. 3) The assembly was delay-signed. 4) A registry key existed that allowed the check to pass (where it would not have otherwise). Sign {0} with a strong name key. http://msdn.microsoft.com/library/ms182127.aspx [none] CriticalError Avoid excessive locals Method implementations should not contain more than 64 local variables. In order for the run-time to enregister local variables most efficiently, there should be 64 or fewer of them. Enregistering based on flow analysis will not occur for locals in excess of 64, which may result in slower performance. {0} has {1} local variables, {2} of which were generated by the compiler. Refactor {0} so that it uses fewer than 64 local variables. http://msdn.microsoft.com/library/ms182263.aspx [none] Warning Do not indirectly expose methods with link demands Do not wrap a method protected by a LinkDemand with a method that does not perform a security check. A LinkDemand checks the permissions of the immediate caller rather than checking the permissions of all callers in the call stack. In this case, the permissions of the wrapper method will be checked. If the wrapper method does not, itself, check the permissions of callers higher in the call stack, malicious code might be able to execute the wrapped function even though it lacks permission to do so. {0} calls into {1} which has a LinkDemand. By making this call, {1} is indirectly exposed to user code. Review the following call stack that might expose a way to circumvent security protection: {2} http://msdn.microsoft.com/library/ms182303.aspx [none] CriticalError Review SuppressUnmanagedCodeSecurityAttribute usage Calling a method with the SuppressUnmanagedCodeSecurityAttribute applied to it can create a security weakness. Unmanaged code security checks ensure that all callers in the call stack have permission to execute unmanaged code. Disabling code security for P/Invoke methods allows callers that do not have this permission to breach security. This is acceptable only if the code is completely harmless, or callers have no way to pass arbitrary arguments through to the unmanaged code. Review declarative security for {0} and its callers for potential vulnerabilities. The following call stack might expose a way to circumvent security protection: {1} http://msdn.microsoft.com/library/ms182311.aspx [none] CriticalError Category Certainty Collapse All Check Id Error error(s) Expand All Help Line message(s) [Location not stored in Pdb] Project Resolution Rule Rule File Rule Description Source Status Target Warning warning(s) Code Analysis Report